论文版本管理器：多稿演进可追踪、可对比、可回滚
论文版本管理器是 SkillHub 社区 Skill（@user_8d26dabd/paper-version-manager，v2.0.10），面向学术论文多轮修改场景：用版本血缘树、四维加权评分、基于审查报告的 P0–P3 CHANGELOG、安全底本与决策审计，让各版修改可对比、可回滚、可审计。无需 API Key，离线基于 read/write。文章说明安装命令、Cursor/Claude/Codex 常见 skills 路径、最小闭环用法及与审稿/投稿、Git 的分工与学术伦理边界。
Read Moredsh-dist-manager: DSH Plugin Distribution Directory Manager
`dsh-dist-manager` is a plugin in the DSH ecosystem for automatically managing the `dist/` directory. It provides version archiving, restoration, and cleanup functions through a WebUI, addressing the error-prone issue of manually managing old files. The plugin supports one-click operations, includes robust error handling and security validation, and manages paths through configuration options. The code is released under the MIT license.
Read Moredsh-update-status: DeepSeek Harness Version Status and Upgrade Guide Plugin
idoall/dsh-update-status is a DeepSeek Harness plugin licensed under the MIT License, designed to provide version status queries and upgrade guidance through a sidebar. It supports light/dark themes and mobile responsiveness, uses Semantic Versioning (SemVer) sorting to compare against the latest npm release, provides update status via color and animation feedback, and generates precise installation commands. The plugin is read-only and does not modify core systems, offering only status display, upgrade guidance, and controlled restart capability (requires a specific environment).
Read Moredsh-version-autoupdate: DeepSeek Harness Version Capsules and One-Click Update
`dsh-version-autoupdate` is a dual-sided Cordis plugin for DeepSeek Harness (DSH), designed to simplify version management in multi-environment deployments through visual floating capsules. The plugin supports npm, pnpm, and Yarn, providing real-time version detection, automatic installation, API integration, and flexible update policies. It supports offline installation and systemd management, but has limitations in desktop edition and non-global installation scenarios: Windows requires a manual restart, while Linux/macOS allow CLI-based updates.
Read Moredsh-version-inventory: DeepSeek Harness Plugin Version Inventory
The `dsh-version-inventory` plugin addresses the pain point of missing version information during DeepSeek Harness (DSH) environment troubleshooting. Maintained by kristol07, it integrates with the Web UI and session tools to provide visual version display and export capabilities. Its core features include reading plugin versions across both the global and preset planes, automatically collapsing configurations and redacting sensitive fields, and detecting distinct version instances of the same package by merging package directories rather than package names. Users can copy version information as a single line or click a table header to export a secure environment report that excludes sensitive paths and configuration data. In addition, the plugin is registered as the `dsh_version_inventory` tool, enabling the agent to invoke it directly within a conversation.
Read Moredsh-version-plugin: View and Update the DSH Version in General Settings
The dsh-version-plugin plugin integrates the DSH runtime version into the settings interface, providing an intuitive version display and update entry. This plugin can read the host-side version and adds a "DSH Version" row at the bottom of the settings, supporting one-click checking for the latest version and executing a global update. It can be installed and used with the official command, but note that updates only apply to global installations, and the `allowBuilds` setting must be configured in pnpm >= 10 environments. After updating, restart the process and refresh the page for changes to take effect.
Read MoreDSH Version Detection | dsh-sm-version-display
The DeepSeek Harness (DSH) Web plugin `dsh-sm-version-display` displays the current version in the sidebar and checks for the latest releases on npm and GitHub. It supports multi-theme adaptation, provides version comparison, one-click updates, and backup management, follows security principles, and is accessible only via the local loopback address. The installation command is `dsh plugin --profile web add @hjj345345/dsh-sm-version-display`.
Read MoreDeepSeek Harness Main Program Version Management Plugin dsh-versions: Safe Upgrades and Rollbacks
The dsh-versions plugin addresses the lack of a rollback mechanism when upgrading the DeepSeek Harness main program. It allows users to view versions and check for updates in the web interface, and supports online installation, reinstallation, and downgrading. With automatic snapshots and second-level rollback, it significantly reduces upgrade risk. The installation requires dsh ≥ 0.1.0 and is Windows-only (as it depends on Windows tools); users on other platforms need to run npm commands manually.
Read Moresatan9394/dsh-git-workflow: Git Workflow and Version Control
dsh-git-workflow is a Git workflow specification plugin for DeepSeek Harness (DSH). It references the agent-skills design philosophy and aims to address disorganized version management. Its core features include trunk-based development, commit discipline, semantic versioning, and automated release workflows. Users need to install it via the official catalog, and it is suitable for scenarios requiring strict version control and standardized commit discipline. For more details, refer to its catalog page or GitHub repository.
Read MoreDeepSeek Harness (DSH) Self-Updating Plugin
dsh-self-updater is a web plugin for DeepSeek Harness (DSH), designed to provide visual version checking, updating, and restarting functionality. It ensures security by accepting only loopback and same-origin requests through HTTP routes. Its core features include precisely installing the latest npm version, automatically restarting the service, monitoring progress, and preserving local data. After installation, users can click the capsule in the top-right corner for one-click updates, making it suitable for developers who need a convenient way to manage DSH versions.
Read MoreDeepSeek Harness Plugin: dsh-update-checker
`dsh-update-checker` is a Profile plugin for DeepSeek Harness (DSH), designed to address compatibility issues caused by toolchain version iterations. When the plugin starts, it automatically checks for new versions in the npm registry and provides a silent GUI notification in the Web interface sidebar. Its core features include non-blocking version checking with a 6-hour cache, an intelligent silent failure mechanism, sidebar interaction pop-ups (displaying version numbers, update commands, and jump links), and support for ignoring specific versions. The plugin has zero disk footprint, automatically adapts to the GUI design system, and uses localStorage to persist ignored versions. Installation requires running the `dsh plugin` command via pnpm, and it is suitable for developers who need frequent updates to access the latest features.
Read MoreGit Branching Strategies: Choosing and Applying GitHub Flow vs. Git Flow
Branch strategies address code conflicts and version management issues in multi-person collaboration, enabling more organized teamwork. The mainstream strategies are GitHub Flow and Git Flow. GitHub Flow is minimalist and flexible, with only two branches: `main` (the main branch) and temporary branches (e.g., `feature/xxx`). The process is straightforward: create a temporary branch from `main`, make modifications, and merge back to `main` via a Pull Request (PR), supporting continuous deployment. Its advantages include simplicity, efficiency, and rapid iteration, making it suitable for personal projects or scenarios requiring quick updates. However, it lacks version planning and is unsuitable for complex version management. Git Flow has clear division of labor with five branches: `main`, `develop`, `feature`, `release`, and `hotfix`. The process is strict, with fixed responsibilities for each branch and phases such as development, testing, and release. It excels in standardization, orderliness, and risk control, making it ideal for large teams or long-term maintenance projects. On the downside, it has a high learning curve and slower iteration speed. Selection recommendations: Choose GitHub Flow for small teams and fast-paced projects; select Git Flow for large teams or projects requiring version management. The core is to ensure smooth collaboration without sacrificing efficiency.
Read MoreGit Tags and Version Releases: Methods for Marking Important Project Milestones
Git tags are a tool that Git uses to create "snapshots" for specific commits. They can mark project milestones (such as version releases), facilitating version location, rollback, and team collaboration. Tags are categorized into annotated tags (recommended for formal versions, created with the -a -m parameters and a description) and lightweight tags (for quick marking without a description). Usage process: Creating tags (local and remote push), viewing (git tag), and deleting (local with git tag -d, remote via git push origin --delete). Version releases follow semantic versioning (major.minor.patch), with tags applied after stable versions, milestones, or urgent fixes. Tags are static snapshots, distinct from dynamic branches (e.g., master), enabling quick rollbacks to historical versions. Mastering tag operations and following a standardized version numbering system can enhance project management efficiency.
Read MoreGit Version Rollback: How to Undo an Incorrect Commit and Retrieve Code
Git version rollback requires scenario-specific handling to avoid sensitive information leaks or code loss. For un-pushed incorrect commits, use `git reset`: `--soft` retains modifications and only undoes the commit, allowing re-submission of correct content; `--hard` completely discards modifications (irreversible, use with caution). For pushed incorrect commits, use `git revert` to create a new undo commit (safe for collaboration), e.g., `git revert HEAD` or specify a hash value. If code is accidentally deleted, use `git reflog` to view operation history, find the target commit hash, then restore with `git reset --hard <hash>`. Note: Prefer `--soft` for un-pushed commits, always use `revert` for pushed commits, avoid `--hard` in multi-person collaboration, and confirm the commit hash before operations.
Read More